How do I Update a Nodinite Log Database?
Keep your Nodinite Log Databases secure, compliant, and up to date with the latest features and performance improvements. This page provides step-by-step instructions, best practices, and troubleshooting tips for updating Log Databases in complex environments.
What you'll find on this page:
✅ Step-by-step guide for updating Log Databases using DACPAC scripts
✅ Best practices for secure and compliant updates
✅ Troubleshooting tips for common update scenarios
✅ Guidance for distributed and large-scale SQL Server environments
All other Core Services parts except the Log Databases are updated using the instructions detailed on the Update Core Service page with the Install and Update Tool.
Keep Nodinite updated to benefit from new features, strengthened security, and bug fixes—ensuring you always get the best experience.
How do I update a Log Database?
Info
You must execute the steps below as the Logging Service account or with an account assigned the sysadmin role.
If you are part of the SYSADMIN fixed server role on all instances hosting a Log Database, you should have sufficient rights to execute the update steps.
Step 1: Select the Environment to update
- Start by selecting the Environment to update:
Example list of installed Environments; select the one to update.
Step 2: Retrieve DACPAC command
The logic behind the scenes uses the value from the LogDatabaseRecovery system parameter to present the correct script information for Log Databases.
The Manual update button is not on the screen if there is no mandatory update available. Otherwise, use the small "..." button to open the modal for optional updates.
Click the button to open a modal with the DACPAC command to execute:
The 'Manual update' button is only available if there's a mandatory update to apply.Copy ALL of the content from the text box
Repeat the step and copy the command text with unique settings for each Log Database.Info
The script has two paths, one for the SQLPackage.exe executable and the second is about the .DACPAC file.
If you execute the update script on another server, you can click the download button to get the proper .DACPAC file.
Important
You must change the path content if you intend to execute the script on another server; please revise and verify the new script accordingly.
Step 3: Execute command
Info
You must perform the update using a command prompt. Do not use the SQL MMC (SSMS) or Powershell.
Info
This step assumes you run the command prompt logged in on the Nodinite server with the Install and Update Tool. It is possible to copy the DACPAC file to another server and adjust folder paths provided to suit the target environment.
- Open an administrative command prompt as either the account running the Logging Service or with another account with at least equal rights or an account part of the SYSADMIN fixed server role on the SQL instance with the Log Databases to update.
- Paste the command string from step 2 and press enter.
Info
You should see text rolling on the screen as the update progresses. This process may take seconds for small databases up to hour(s) for large databases or SQL Servers with poor disk IO performance.
- Repeat "Step 2" and "this Step" for all Log Databases listed for an update (with the Manual Update button).
Info
The Configuration Database may be in the list with the Manual Update button.
[!NOTE] This database is usually updated by the system during the update process. Use the script only if there's a problem executing the update from the Install and Update Tool. - You may need to perform a shrink operation. Make sure to review the allocated disk space on your SQL Server instance with the updated Nodinite Log Databases.
Frequently asked questions
Find solutions to common problems and answers to frequently asked questions in the Nodinite Log Databases FAQ, available in the Troubleshooting user guide.
Why can't we update Nodinite Log Databases from the Install and Update Tool?
There are many reasons why the system cannot update the Log Databases automatically as part of the update process. There may be multiple Log Databases scattered over several SQL Server instances, even on different networks running with a plethora of different security-related account settings. Also, these Log Databases may be very large; rebuilding indexes, changing tables, and more can take hours to complete. Since the Install and Update Tool is a web-based interface, there is no way of keeping a responsive GUI. Therefore, you must update Nodinite Log Databases manually.
Please help, I have been trying to update on another server, and the script fails immediately
The following problems are common:
- The path to the SqlPackage.exe is wrong (the path set with the version found on the server with the Install and Update Tool).
- The path to the .DACPAC file is wrong (the path set with the unpacked file on the server with the Install and Update Tool).
- You do not have sufficient rights to modify the Log Databases.
The Nodinite Logging Service uses the System Parameter SqlPackageExecutable to spawn new Log Databases.
Next steps
Update Nodinite
Nodinite Release notes